home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: Re-starting GEM
- Date: Tue, 24 May 94 20:45:00 CDT
- From: Juergen Lock <nox@jelal.north.de>
- In-Reply-To: <m0q599j-0000lPC@sdf.lonestar.org>; from "Evan K. Langlois" at May 22, 94 3:45 am
- Message-Id: <9405241845.AA00559@jelal.north.de>
-
- Evan K. Langlois writes:
- > OK, someone asked how to start/stop GEM without losing memory and such.
- > Here is a method that works.
- >
- > I'm sure that everyone knows you can use CNTRL-ALT-C to kill GEM. If you
- > started GEM from a SHELL, you get your shell back. You can sometimes run
- > a GEM application from the shell after you've killed the GEM desktop.
- > Since GEM has already initialized the program can still call GEM, however,
- > sometimes tyhe screen manager or something gets left in a weird state.
-
- uuhuu, that might end up accessig freed memory...
- >
- > SO! Try the following. Boot into a shell that supports good job control.
- > I found that sh03 whatever binary was not adequate (I think this is ash).
- > Bash has funky problems on my console when I run NVDI, so I used TCSH.
- > You run GEM in the background!! If TCSH doesn't suspend GEM for TTY input
- > when you start pressing keys, then simply press CNTRL-ALT-Z to stop GEM.
-
- sure, thats possible (and is even easier with virtual consoles :)
-
- > the shell, SIGSTOP GEM again. This doesn't free the memory that GEM
- > uses, but it's about as close as its gonna get without some really nasty hacks
- > I think.
-
- i think some of the memory is actually freed, but all the vectors still
- point to it! ah well, if GEM just knew about signals...
-
- cheers
- Juergen
- --
- J"urgen Lock / nox@jelal.north.de / UUCP: ..!uunet!unido!uniol!jelal!nox
- ...ohne Gewehr
- PGP public key fingerprint = 8A 18 58 54 03 7B FC 12 1F 8B 63 C7 19 27 CF DA
-